# Conflicts:
#	.github/workflows/ci.yml
#	docs/usage.md
#	src/xdp/precomp.h
#	src/xdp/program.h
#	src/xdp/xdp.vcxproj
#	xdp.sln

… runtime

The rxfilter/xskfwd/xskrestricted sample tests load native XDP eBPF programs
(drop.sys / xsk_redirect.sys), which require XDP's eBPF program-information
provider. That provider is only registered when XDP is installed with
-EnableEbpf. Without it, program load fails with eBPF error 23 (failed to load
program information) and the sample exits with code 1.

xdpbpfexport.exe (run by 'setup.ps1 -Install xdp -EnableEbpf') links
EbpfApi.dll, so the eBPF runtime must be installed first. Reorder the sample
tests to install eBPF before XDP (and uninstall XDP before eBPF), matching
functional.ps1. Fixes xdpbpfexport 0xC0000135 (STATUS_DLL_NOT_FOUND).

Validated on hardware: rxfilter sample now processes traffic and passes.

The functional trace profile captures TraceInfo but not TraceVerbose, so the
XskCanRedirect diagnostic was not appearing in CI logs. Promote it to TraceInfo
and add an EbpfXdpRedirectMap decision summary (key, flags, fallback action,
returned action) so the arm64-only redirect fallback failures can be diagnosed
from the next CI run's logs.

…k path

- Sample tests: uninstall eBPF before XDP so the eBPF redirect program + XSK are
  torn down before xdp restarts (xskfwd force-kills its loader, leaving the
  program attached; with XDP uninstalled first the xdp restart hangs). Install
  order stays eBPF-first for xdpbpfexport.
- Redirect diagnostics: only trace XskCanRedirect==FALSE and the RedirectMap
  fallback path, so high-volume redirect-success traces don't flood the ETL and
  drop the low-volume fallback-test events needed to diagnose the arm64 failure.

# Conflicts:
#	tools/common.ps1

With eBPF uninstalled first, the xdp uninstall's xdpbpfexport --clear fails with
0xC0000135 (EbpfApi.dll already gone), leaving xdp loaded and failing the post
Check Drivers step. Pass -Force so that failure is downgraded and xdp is fully
removed.

The eBPF XSKMAP (bpf_redirect_map to AF_XDP) requires the eBPF for Windows
base-map-provider, available in v1.3.0+. functional.ps1 exports the installed
runtime version via XDP_EBPF_RUNTIME_VERSION; the eBPF XSKMAP tests skip when it
is older than 1.3.0. Adds a SkipTest framework primitive and TEST_SKIP macro.

…irect

Use acquire loads for the lockless reads of XSK State and bound RX queue in
XskCanRedirect, and a matching release store when teardown transitions State
to XskClosing. On weak memory-ordering architectures (arm64) plain loads could
observe a stale state and wrongly redirect to a closing socket instead of
falling back. Remove the temporary redirect diagnostics.

…fallback

The arm64/1.3.0 GenericRxEbpfXskRedirectCloseSocket and QueueMismatch failures
are deterministic (Debug and Release), ruling out the memory-ordering race the
acquire/release change targeted, so revert it. Both failing tests are the only
ones passing a runtime fallback value to bpf_redirect_map (via
xsk_redirect_fallback). Add a results map to that eBPF program recording the
rx_queue_index and fallback action it computes, and read them back in the test
(with a diagnostic warning) to isolate an eBPF-side miscomputation from an
XDP-side helper issue.

The arm64 diagnostic confirmed the eBPF program computes the correct rx_queue_index
and fallback action, so the drop is XDP-side. Record the value returned by
bpf_redirect_map (results_map[2]) and log it, to determine whether the kernel
decided XDP_REDIRECT (XskCanRedirect wrongly returned TRUE) or returned the
fallback action (drop occurs deeper in the datapath).

The 128-char TAEF warning buffer truncated the combined diagnostic before
ProgAction printed, so emit the bpf_redirect_map return action on its own short
line. Add low-volume kernel WPP TraceInfo in XskCanRedirect (State/XskQueue/
RxQueue/CanRedirect) and EbpfXdpRedirectMap (Key/Flags/Xsk) to capture the exact
redirect-decision inputs for the arm64-only redirect fallback failures. These
paths are only exercised by the eBPF XSKMAP redirect tests, so the traces are
low volume and retrievable from the functional ETL artifact.

…atapath

XdpInvokeEbpf built EBPF_XDP_MD on the stack without initializing ProgTestRunContext. EbpfXdpRedirectMap reads IsProgTestRun = (ProgTestRunContext != NULL); on arm64 the uninitialized stack slot was non-NULL, so real datapath frames were misclassified as prog_test_run, skipping XskCanRedirect and unconditionally returning XDP_REDIRECT. This broke GenericRxEbpfXskRedirectCloseSocket and GenericRxEbpfXskRedirectQueueMismatch on arm64 (deterministic). Initialize ProgTestRunContext = NULL on the datapath. Also removes the temporary diagnostic instrumentation (results_map in xsk_redirect_fallback.c, TEST_WARNING diagnostics in tests.cpp, and kernel TraceInfo in xsk.c/program.c).